Transmission, via determinative logic, of electronic documents for sharing and signing (“TESS”)

ABSTRACT

Aspects of the disclosure relate to a transmission logic for selecting an authorized signatory as a recipient for an electronic document for signature. The transmission logic forms a part of a communications platform. The platform, including a first electronic communications pathway and a second electronic communications pathway, conducts and supports communication between a first entity and a second entity. The logic may generate an electronic document together with a request for an electronic signature, flag the document and transmit the document along the first electronic communications pathway to an authorized signatory at the second entity. The logic may also select a signatory according to a predetermined protocol, determine the availability of the selected signatory, confirm the selection, and transmit the electronic document to the authorized signatory for signature. Upon notification of the electronic signature, the logic may transmit, along the second pathway, the document to the first entity.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.16/400,275 filed on May 1, 2019 and entitled TRANSMISSION, VIADETERMINITIVE LOGIC OF ELECTRONIC DOCUMENTS FOR SHARING AND SIGNING(“TESS”) which is hereby incorporated by reference herein in itsentirety.

FIELD OF TECHNOLOGY

Aspects of the disclosure relate to electronic document sharing andsigning. Specifically, aspects of the disclosure relate to electronicdocument sharing and signing with a heretofore unknown recipient. Forthe purposes of this application, the term “document” or “document(s)”referred to herein should be understood to refer to electronicdocuments. The terms “sharing” and “signing” referred to herein refer tothe electronic sharing and electronic signing of electronic documents.

BACKGROUND OF THE DISCLOSURE

Corporate entities have a need to exchange documents and agreements witheach other. In some situations, two cooperating entities do notnecessarily know each other's signatory requirements or internalpolicies regarding same. In other situations, two cooperating entitiesmay know each other's signatory requirements or internal policiesregarding same. In yet other situations, one of two cooperating entitiesmay know the other's signatory requirements or internal policies. Inconventional systems, these entities have to manually share expectationsregarding sharing and saving e-documents and hope the other partyfollows their respective rules.

Often a corporate entity faces difficulties with a document signaturesystem. For example, maintaining an authorized signer database (for thepurposes of this application the terms “signer” and “signatory” areinterchangeable and refer to the one signing and/or affixing his or herelectronic signature to the electronic document) can be difficult andmay take long periods of time to update. A corporate entity's workflowis neither connected nor necessarily aligned with other entities—evenwith entities with which the corporate entity is cooperating. Such anon-aligned workflow may be non-aligned because of dual signer policies,limits associated with certain signers, etc.

In addition, a cooperating entity may be responsible for maintainingcorporate-entity-client authorized signer lists but clients do notalways let the cooperating entity know about changes to such lists (orto the contents of the lists in general.) And, as mentioned above, theremay be workflow divergence between a corporate entity and a cooperatingentity. For example, a corporate entity may require a change put throughthe system immediately, but the cooperating entity may be working onmultiple-day service level agreement. As such, the cooperating entitymay only be scheduled, and/or expected, to put through such a changeover a multiple-day interval instead of immediately. Finally, theavailable signatories at any given time, or across a window of time, maynot be known even to the corporate entity. As such, obtaining authorizedsignatures on certain documents that are sent to an unavailable signermay be delayed.

Typically, corporate entities need to control the individuals authorizedto sign on behalf of the entity. Corporate entities also want to be ableto access, and, when necessary, change their list of authorized signers.In addition, corporate entities need to be able to require that signersconform to internal policy and directives. Also—corporate entities oftendemand additional visibility into status of submitted documentationrelated to requests.

Counterpart entities (referred to herein in the alternative as“cooperating entities”) to the corporate entities may be recipients ofelectronically-signed documents from, or may exchangeelectronically-signed documents with, the corporate entity. Suchcounterparts may also have various needs related to document sharing andsigning.

Under certain circumstances, corporate entities may want to maintain adynamic roster of authorized signers. Under such circumstances, all, orsome, members of the list of authorized signers may be unknown tocooperating entities such as entities who are attempting to exchangeelectronic documentation with the corporate entity for signature by theauthorized signatories of the corporate entity.

Also, the corporate entity typically, to the extent possible, wants tomaintain the confidentiality of its signers.

Accordingly, it would be desirable to provide systems and methods fortransmission, via determinative logic, of electronic documents forsigning and sharing (TES S).

SUMMARY OF THE DISCLOSURE

Aspects of the disclosure relate to transmission, via determinativelogic, of electronic documents for signing and sharing (TESS). TESS maybe implemented via a platform for communication between a first entityand a second entity. TESS may be implemented via logic resident at anentity that receives, for authorized signature, an electronic document.TESS may be implemented in response to receipt of a request for anelectronic document and signature thereon. TESS may be implemented, inone alternative embodiment, on the transmitter-side of a request forsignature on an electronic document.

An aspect of the disclosure may include a method for receiving androuting an agnostic request for electronic signature on an electronicdocument. The request may require an electronic signature by anauthorized signatory. The method may include selecting, usingtransmission logic, an authorized signatory. The selection may be fromamong a plurality of authorized signatories. The selection may be fortransmission thereto, of an electronic document for electronic signatureby the selected authorized signatory. The transmission logic may form apart of a communication system located at a first entity. Thecommunication system may be in line with a communication platform.

The communication system may include a first electronic pathway. Thecommunication system may include a second electronic pathway. Thecommunication platform may be for communicating between the first entityand a second entity. The second entity may be associated with thegeneration of the preferably agnostic request.

The transmission logic may be configured to receive the electronicdocument along the first electronic pathway. The transmission logic maybe further configured to access a list of the plurality of authorizedsignatories. The transmission logic may also be configured to determinethe availability of an authorized signatory from among a list of theplurality of authorized signatories. The determining may be effectedaccording to a predetermined protocol.

When the authorized signatory is determined to be available, the methodmay include selecting the authorized signatory from among the list ofplurality of authorized signatories. The method may also includetransmitting the electronic document to the authorized signatory foraffixing the electronic signature to the electronic document. The methodmay further include, upon notification of the affixing of the electronicsignature to the electronic document, transmitting, along the secondelectronic pathway, the electronically signed electronic document to thesecond entity.

BRIEF DESCRIPTION OF THE DRAWINGS

The objects and advantages of the disclosure will be apparent uponconsideration of the following detailed description, taken inconjunction with the accompanying drawings, in which like referencecharacters refer to like parts throughout, and in which:

FIG. 1 shows an illustrative checklist in accordance with principles ofthe disclosure;

FIG. 2A-2C show schematic illustrations of a hybrid method/system inaccordance with principles of the disclosure; and

FIG. 3A-3C show schematic illustrations of transmission, viadeterminative logic, of electronic documents for sharing and signing(“TESS”) in accordance with principles of the disclosure.

FIG. 4 shows another schematic illustration of transmission, viadeterminative logic, of electronic documents for sharing and signing(“TESS”) in accordance with principles of the disclosure.

DETAILED DESCRIPTION OF THE DISCLOSURE

Conventional electronic systems for processing documents for obtainingelectronic signatures utilize standard databases. One database residesat the corporate entity together with the authorized signatories. Onedatabase resides at the cooperating entity tasked with obtaining thesignatures from one or more of the authorized signatories.

Typically, the conventional electronic systems only possessed theability to route to known authorized signatories. However, such routingto known authorized signatories required that the visible/and/authorizedsignatories be visible to participants in the communication chain alongthe communication pathway. In fact, the identity of suchvisible/and/authorized signatories are, by definition, open andavailable to each participant along the transmission path.

This conventional process involves two challenges. First, it requiresthat participants at the electronic document-generating entity identifyan authorized signatory. Such identification requires that theparticipants at the electronic document-generating entity also contactthe authorized signatory to determine availability of the identifiedauthorized signatory. In short, whether the electronic documentoriginated at the corporate entity or at a cooperating entity, theconventional systems required that both entities needed to know theidentity of the authorized signer prior to processing the electronicdocument for signing.

This added layer of identification, and subsequent contact, requiresadditional resources—both computer resources in the case of electroniccorrespondence and scheduling regarding same, and human resourcesrequired to make the contact and confirm availability.

Second, the process exposes the identity of one or more of theauthorized signatories to the electronic document-generating entity.This may compromise the security of the identities of the authorizedsignatories by unnecessarily exposing their identities to members of theelectronic document-generating entity as well as to unqualifiedemployees of the entity at which the authorized signatories are located.This may also require, in certain circumstances, substantiallycontinuously synching the database of the electronic document-generatingentity and the database of the entity at which the signatories reside.This synching is required because the electronic document-generatingentity requires up-to-date information regarding the identity of theauthorized signatories.

In some circumstances, such as one in which an electronic-documentreceiving employee is only of temporary status, it may not be desirablefor the corporate entity to expose identification ofvisible/and/authorized signatories to temporary or other workers withinthe entity itself.

In some embodiments, system logic may route the electronic document fromthe electronic document-generating entity to the entity at which theauthorized signatories reside. At the entity at which the authorizedsignatories reside, the document may be identified, categorized and thentransmitted to one or more of the authorized signatories.

In other embodiments, even at the incoming point of the entity at whichthe authorized signatories reside, the identity of the authorizedsignatory may remain hidden. Such embodiments may preferably utilize aflag, or other indicator, that an authorized signatory is required.However, the identities of the list of authorized signatories in suchembodiments would preferably remain hidden and/or masked from theoriginator of the request. Although the authorized signatory will becomeknown once the executed document is returned to the originator, theseembodiments preferably maintain security of the list of authorizedsignatories to a relatively higher level than previously considered.

These embodiments may maintain secrecy of the authorized signatory evenwithin the entity at which the authorized signatory resides. In someembodiments, the identity of the authorized signatory may not be knownon the outgoing document as well. The identity of the authorizedsignatory may, in such embodiments, be maintained in secrecy until thedocument arrives at the document generator and/or requestor. Such anembodiment could, in certain circumstances such as when the two partiesagree, effectively switch responsibility for confirming theauthorization of the identity of the authorized signatory to thecorporate entity to ensure at which the signatory resides.

Accordingly, a temporary worker at the corporate entity could receivethe document and send it along for routing by a routing web to anauthorized signatory without knowing the list of authorized signatories.

In certain such embodiments, the corporate entity itself would not knowthe list. Rather only certain, select, representatives within thecorporate entity would know the list of authorized signatories.

It should be noted that some embodiments may involve a different routingrail—i.e., electronic transmission pathway—for incoming transmissionsand a different routing rail for outgoing transmissions. Accordingly,such embodiments may enable, along a first rail, receipt of an incomingtransmission of an electronic document in need of signature that doesnot specify an authorized signatory. Such embodiments may include logicfor routing the incoming transmission to a predetermined signatoryaccording to a predetermined protocol.

Such embodiments may also enable an outgoing transmission. Such anoutgoing transmission may specify involve a different routing rail outof the corporate entity for the signed electronic document. In suchcases the incoming rail might indicate that the document was sent to ato-be-determined authorized signatory. The outgoing rail may indicatethat the signed document be executed by a different rail, with a knownauthorized signatory.

It should be noted that a record of authorized signatories internal tothe corporate entity could be handled by only an appropriate, andpreferably pre-determined, level of entitlements—i.e., employeesassociated with a pre-determined level of clearance within an entity,preferably along a first rail. In this architecture—the access tosignatories could be controlled according to the level of theentitlement of the actor involved with the incoming documents. Theaccess to outgoing documents could also be controlled by a second levelof entitlement.

In short, the first rail may specify a first level of entitlements—forprocessing raw incoming electronic transmissions. The raw incomingelectronic transmissions preferably does not specify an authorizedsignatory. In certain embodiments, the first level of entitlements mayhave access to an internal list of signatories. In some embodiments, thefirst level of entitlements have no access to the internal list ofsignatories.

An extension of rail 1 may specify a second level of entitlement andpreferably provide for routing the raw incoming electronic transmissionsto an authorized signatory (either user-defined, or system-set.) Theauthorized signatory could then affix an electronic signature.

Rail 2 may be for outgoing transmission of signed electronic documents.Such use may also specify a second level of entitlement. The secondlevel of entitlement may involve employees that are entitled to accessand/or have knowledge of the identities of authorized signatories.

The systems and methods according to the system preferably involvearchitecture with logic. The logic preferably saves time for determiningand contacting authorized signatory. One reason that such systems andmethods conserve resources is that the cooperating entity is notrequired to possess the database including the authorized signatories.In such circumstances, the cooperating entity also does not have toresort to other entities in order to access information regarding theauthorized signatories. Preferably, the corporate entity may maintainthe database of authorized signatories.

In certain embodiments of the invention, the authorized signatoriesdatabase could be made available on an internal, preferably restricted,e-mail, web or other electronic system. Further, access to one more of aplurality of authorized signatories could be determined by determinativelogic.

In some embodiments, documents may be categorized according to one ormore document types. Such document types may be directed by the logic todifferent lists according to different categories and/or levels ofentitlements associated with the categories. For example, a request forsignatories relating to an “opening accounts” document may retrieve onelist of authorized signatories, and a request for signatories relatingto an “adding services” could retrieve a second list of authorizedsignatories.

In preferred embodiments, the logic may be adjustable with respect tothe identification of the recipient of the document. For example, thelogic should preferably create a new drop down menu for the corporateside. The drop down menu may preferably enable the corporate side tohave the option of manually and/or automatically routing the electronicdocument for signature.

In certain embodiments, an API resident at the corporate entity, or inany other suitable location, may preferably enable a user, or thesystem, to conform the electronically-signed document to the providedelectronic document requirements among other things.

Such conforming may involve the following configuration issues. Forexample, the API may configure the following aspects of theelectronically-signed document to the provided electronic document:

1) Signer Definition

2) Document Categories;

3) System-Setting Parameters;

a) cc copy to a dedicated mailbox

b) subject-line information; and/or

c) other suitable configuration items; and

4) Varying cooperating entities might specify different configurations.

Often, the foregoing configuration issues relating to the variouscooperating issues involve common terminology/definition/mapping offields. Attention to these issues may consume additional resources. Suchadditional resources may be drawn from the originator of the electronicdocument.

A transmission logic for selecting an authorized signatory from among aplurality of authorized signatories is provided. The transmission logicmay enable transmission of an electronic document for electronicsignature by the selected authorized signatory. The transmission logicmay form a part of a communication system located at a first entity. Thecommunication system may be part of an architecture that includes acommunication platform. The communication system may be in line with thecommunication platform. The communication system may include a firstelectronic pathway and a second electronic pathway. The communicationplatform may enable communication between the first entity and a secondentity.

The transmission logic may be configured to receive, from along thefirst electronic pathway, the electronic document together with arequest for signature by one of a group of authorized signatories. Thetransmission logic may also be configured to access a list of theplurality of authorized signatories.

The transmission logic may be configured to determine the availabilityof an authorized signatory from among the list of the plurality ofauthorized signatories. The determining may be effected according to apredetermined protocol. Such a protocol may involve an algorithm basedon various factors. Such factors may include availability of thesignatory, level of entitlement of the signatory, categorization of theelectronic document and/or any other suitable factor associated with theselection of the signatory.

When the authorized signatory is determined to be available, the logicmay proceed to select the authorized signatory from among the list ofplurality of authorized signatories. Following selection of theauthorized signatory, the logic may instruct the system to transmit theelectronic document to the authorized signatory for affixing, orotherwise electronically signing, the electronic signature to theelectronic document.

Upon notification of the affixing of the electronic signature to theelectronic document, the logic may instruct the system to transmit,preferably, but not necessarily, along the second electronic pathway,the electronically-signed electronic document to the second entity.

In certain embodiments, the electronic document may include anelectronic signature applied by a signatory to a location on each of thedocuments that corresponds to a predetermined and preferably embeddedfield tab.

In some embodiments, the protocol may include a ranking of authorizedsignatories defined by one or more predetermined metrics. Thepredetermined metrics may include, for example, the level ofavailability of the authorized signatories. The protocol may alsoinclude a ranking of authorized signatories defined by two or morepredetermined metrics. The two or more of the predetermined metrics mayinclude the level of availability of the authorized signatories and theseniority or level of entitlement of the authorized signatories. Whenthe protocol determines that a selected signatory is not available forelectronic signature, the protocol may require signature by two or moreauthorized signatories on the electronic document.

Specifics of a shared ecosystem according to certain embodiments follow.The embodiments are described in conjunction with FIGS. 1-3 .

FIG. 1 shows a preferably client-initiated eSignature checklist 100 foruse with certain embodiments. In certain embodiments, such a checklistmay be complemented by an API. The API preferably enables clients toauto-adjust their respective TESS account settings and template forsending electronic documents to a cooperative entity. It should be notedthat, while FIG. 1 shows a preferably client-initiated eSignaturechecklist 100 for use with certain embodiments, the same or otherembodiments may involve a similar checklist for use at the cooperatingentity side of the API. Such a cooperating entity-initiated eSignaturechecklist may be used to allow the cooperating entity to generate thee-signature checklist.

A corporate client may be provided with such a checklist, as shown inFIG. 1 . The checklist preferably outlines the actions a corporateclient takes in order to initiate a signed-document transmission to, orexchange with, a cooperative entity. Such actions enable the corporateentity to participate in a TESS ecosystem as set forth herein.

The client-initiated eSignature checklist 100 preferably includes atleast two sections—1) Requirements to submit using a TESS 102 and 2)Preparing documents for delivery to the cooperative entity 104. Theclient-initiated eSignature checklist 100 may, in certain embodiments,further include a message to all recipients 106.

Requirements to submit using a TESS 102 preferably detail that a userneeds an active TESS account; documents and letters of instruction forUnited States (US) accounts and/or US relationships; and details ofknown signer profiles such as name title, and uploaded image ofsignature specimen for known signatures, and the ability to work with acooperating entity to effect a test message.

To the extent that not all signatories should be available to allemployees of the client entity, more some, or all of the signatories maybe available in this checklist, or in a document dropdown associatedtherewith. In the absence of known signatories, the system may enable auser to submit the document without identifying a known signatory andhave the system route the document according to the predeterminedprotocol. In certain embodiments, such submission may preferably berouted along a first communication rail, as described in more detailabove.

Preparing documents for delivery to the cooperative entity 104 mayinclude the following instructions. The instructions may includepreparing documents or letters, loading such letters to TESS, and addingfield tags for signers. Field tags for signers can be specified in oneof two ways: 1) Passing the explicit x/y coordinates of each tab in thexml when creating the Envelope. This is appropriate for documents with astandard format, where the signature lines and/or other data itemscollected by the tabs are always located in the same place on thedocument. In this scenario, the xml request describes where to locatethe tabs. 2) Specifying “anchor” strings that exist in the document,against which the tabs should be placed. This is appropriate fordocuments that have variable content/format, where the tab locationsmust similarly vary. In this scenario, the xml request describes how tolocate such tabs.

In addition, the instructions may include the ability to edit recipientsto add a cooperative entity as a “cc receives a copy” recipient. Also,the instructions may include selecting a “set signing order” to ensurethe document is only delivered to a cooperative entity after signatorieshave been determined, located and the document has been fully executed.Finally, the instructions may include directing the cooperative entityto be the last address in the order, and using a dedicated cooperativeentity group e-mail address for delivery. In certain embodiments, thecooperative entity side logic may be invoked to route the electronicdocument for signature according to a pre-determined protocol. In someembodiments, the cooperative entity side logic may be invoked to routethe received electronic document to a predetermined recipient at thecooperating entity.

In certain embodiments, the instructions may further direct the user touse “Edit Message” to add to the company name and TESS envelope ID toconfigure the subject line of each request, and then to send thedocument. The cooperative entity may then receive the final executedcopy directly from TESS, saving the added step of saving the documentand attaching it to the e-mail for transmission to the cooperativeentity.

FIGS. 2A-2C shows preferably client-initiated e-signature processes 200.One or more client-based, authorized, signatories 202 are shown. Itshould be noted that while signatories 202 are authorized, they stillrequire authentication at the time of applying their signatures. Thus,in order to electronically sign a document, a signatory 202 mustpreferably authenticate his identity to the system. Such authenticationmay involve using one or more password(s), biometric authentication, acombination of two or more of the foregoing, or any other suitableauthentication.

TESS 204 may preferably host the checklist shown in FIG. 1 (above) TheTESS 204 may preferably include the list of authorized signers shown at202. Thereafter, electronically signed documents 206 may preferably bereceived by, and/or exchanged with, the cooperative entity at 208.

FIG. 2A shows that an e-signature process may be initiated by aclient-entity-side employee 202. Such an employee may initiate theprocess shown in FIG. 2A by completing the checklist shown in FIG. 1 .Upon completion of the checklist, the process shown in FIG. 2A maypreferably transmit an electronic document 206, once signed from one ofthe employees to the logic block 203. Thereafter, the routing of theelectronic document 206 may be completed, via TESS 204, to cooperatingentity 208.

FIG. 2B shows that an e-signature process may be initiated by acorporate-entity-side employee 208. Such an employee 208 may initiatethe process, but preferably without making contact, or, in someembodiments, even identifying a client side employee 202. In suchembodiments, logic block 203 may preferably route electronic document206 to an appropriate and preferably authorized signer. The routing maybe controlled by a predetermined protocol. Following identification andselection of an authorized signatory, logic block may preferably routethe unsigned electronic document to the appropriate authorizedsignatory.

FIG. 2C shows a cooperating-entity-side logic block 205. Such a logicblock 205 may preferably perform the same or different functions thanlogic block 203. In certain embodiments, where logic block 205 isperforming different functions from logic block 203 and the samefunctions, logic block 205 may preferably be used to perform routingfunctions, as necessary, at the cooperating entity 208, and/or route theelectronic document to an identified authorized signatory at the cliententity 204. Logic block 205 may also preferably route the electronicdocument, once executed, to an appropriate location within thecooperating entity 208.

FIG. 3A-3C show illustrative embodiments of an architecture according tocertain principles of the disclosure. The corporate entity is shown at302. A cooperating entity is shown at 324. FIG. 3A resembles theschematic illustration shown in FIG. 2A to the extent that in both FIGS.2A and 3A, the client entity side initiates the transaction. FIG. 3Bresembles the schematic illustration shown in FIG. 2B to the extent thatthe cooperating entity side initiates the transaction. FIG. 3C resemblesthe schematic illustration shown in FIG. 2C to the extent that the logicblock has been moved to the cooperating entity. It should be noted that,in certain embodiments, a logic block may disposed both at the cliententity as well as the cooperating entity.

Corporate entity 302 may include an organizational person 304. Corporateentity 302 may also include firewall 306. Corporate entity 302 may alsoinclude user information 308 and a key manager 310. User information 308may include controls 309. Corporate entity 302 may also include a signerdatabase 316. Signer database 316 may preferably be deployed incommunication with logic block 311. It should be noted that in FIGS.3A-3C signer database 316 is preferably located and protected withincorporate entity 302.

TESS may, in certain embodiments also include controls 313 provided bythe business.

Organizational person 304 may preferably be a corporate entity assigneeresponsible for directing and/or arranging the electronic signing andsharing.

Firewall 306 may preferably protect corporate entity 302 from anymalware or other damaging information being transmitted through cloud312.

TESS 311 may access cloud 312. Organizational person 304 may alsocontrol a lock 314 located in TESS. Lock 314 may preferably governaccess from corporate entity 302 to cloud 312. It should be noted that,in certain embodiments, TESS may take the form of, or include, anApplication Program Interface (API).

Authorized signers 320 are shown schematically. Electronically-signabledocuments are shown schematically at 318. Accordingly, one of theauthorized signers 202 or other employee 205 of the client entity maypreferably leverage TESS 204 to initiate an e-signature processaccording to some embodiments, as shown schematically in, inter alia,FIG. 2A. Such an e-signature process may be initiated, by companyemployee 205 or other suitable initiator, independent of knowledge ofwhich client-entity employee will execute the document.

At FIG. 2B, the logic block 203 is shown as located between TESS andclient-side authorized signers 202. Logic block 203 may preferablydetermine, according to a pre-determined protocol, the client-sideauthorized signer for signing the electronic document. The electronicdocument 206 may be self-generated from within client entity 202. Insome embodiments, electronic document 206 may be received fromcooperating entity 208. Electronic document 206 may preferably be shownas transmitted received from or transmitted to (following signature) tocooperating entity 208.

It should be noted that FIGS. 2A-2C show first rail 209 and second rail211. In certain embodiments, an electronic document 206 received fromcooperating entity 208 absent specification of an authorized signatorymay be received at client entity 202 via first rail 209. Followingexecution, electronic document 206 may be transmitted back tocooperating entity 208, via logic block 203 and routed across secondrail 211.

In some embodiments, a self-generated electronic document 206 receivedfrom within client entity 202 absent specification of an authorizedsignatory may be sent and routed through logic block 203. Followingexecution, electronic document 206 may be transmitted back tocooperating entity 208, via logic block 203 and routed across secondrail 211.

Signer database 316 may include one of several configurations. Forexample, in certain embodiments, signer database 316 may be read from orwritten to by selected members of entity 302. In certain embodiments,access to database 316 may preferably be controlled. Such control mayinclude enabling access to pre-determined levels of entitlements. Suchaccess may, in certain embodiments be limited to one or more preferablypre-determined communication rails.

In some embodiments, signer database 316 may be read from or written toby entity 302 and only read from by entity 324. In such embodiments,entity 302 may preferably entrust entity 324 with knowledge of itssigner database 316, but maintain complete control of the contents andauthorizations of signer database 316.

Such a configuration—i.e., wherein database 316 may be read from orwritten to by entity 302 and only read from by entity 324 (and even, incertain embodiments, masked and/or hidden in whole or in part fromcooperating entity 324)— may enable the transmission of electronicallysigned documents 318 from entity 302 to entity 324. In certainembodiments, entity 302 may bear the responsibility of verifying thepropriety of the electronic signatures—using access to database 316.

It should be noted further that preferably all of the embodimentsdisclosed herein require that each of entity 302 and entity 324 areaccessible only by a suitable software key. Such software keys may be inthe possession of key managers shown schematically at 310, 322 and 332.

FIG. 4 shows another schematic illustration of transmission, viadeterminative logic, of one or more electronic documents 406 for sharingand signing (“TESS”) in accordance with principles of the disclosure. At402, FIG. 4 shows a cooperating entity sending an e-document forexecution to a client entity. As part of the transmission, thecooperating entity specifies the e-document and configures thee-document to the specifications of the client entity. In someembodiments, no signatory is defined in the transmission.

The client entity is shown at 408. At client entity 408, theidentification of signers is stored in database 411. Upon receipt,e-document 406 is preferably transferred to logic 410. Block 410preferably selects one or more of signers 412 for transmission to, andsignature or, e-document 406.

The steps of methods may be performed in an order other than the ordershown and/or described herein. Embodiments may omit steps shown and/ordescribed in connection with illustrative methods. Embodiments mayinclude steps that are neither shown nor described in connection withillustrative methods.

Illustrative method steps may be combined. For example, an illustrativemethod may include steps shown in connection with another illustrativemethod.

Apparatus may omit features shown and/or described in connection withillustrative apparatus. Embodiments may include features that areneither shown nor described in connection with the illustrativeapparatus. Features of illustrative apparatus may be combined. Forexample, an illustrative embodiment may include features shown inconnection with another illustrative embodiment.

The drawings show illustrative features of apparatus and methods inaccordance with the principles of the invention. The features areillustrated in the context of selected embodiments. It will beunderstood that features shown in connection with one of the embodimentsmay be practiced in accordance with the principles of the inventionalong with features shown in connection with another of the embodiments.

One of ordinary skill in the art will appreciate that the steps shownand described herein may be performed in other than the recited orderand that one or more steps illustrated may be optional. The methods ofthe above-referenced embodiments may involve the use of any suitableelements, steps, computer-executable instructions, or computer-readabledata structures. In this regard, other embodiments are disclosed hereinas well that can be partially or wholly implemented on acomputer-readable medium, for example, by storing computer-executableinstructions or modules or by utilizing computer-readable datastructures.

Thus, methods and systems for transmission, via determinative logic, ofelectronic documents for sharing and signing (“TESS”) are provided.Persons skilled in the art will appreciate that the present inventioncan be practiced by other than the described embodiments, which arepresented for purposes of illustration rather than of limitation, andthat the present invention is limited only by the claims that follow.

What is claimed is:
 1. A system for routing an electronic document to anunidentified authorized signatory, the system comprising a communicationsystem located at a first entity, said communication system being inline with a communication platform, said communication system comprisinga first electronic pathway associated with a first level of entitlementand a second electronic pathway associated with a second level ofentitlement, said communication platform for communicating between thefirst entity and a second entity, said communication system comprisingtransmission logic configured to: receive, from along the firstelectronic pathway, the electronic document together with a request forsignature; access a list of the plurality of authorized signatories in arestricted database maintained by the first entity; determine theavailability of an authorized signatory from the list of the pluralityof authorized signatories, said determining being effected according toa predetermined protocol, the protocol comprising a ranking ofauthorized signatories defined by one or more predetermined metrics,wherein one of the predetermined metrics comprises a level ofavailability of the authorized signatories; when the authorizedsignatory is determined to be available, select the authorized signatoryfrom the list of the plurality of authorized signatories; transmit theelectronic document to the authorized signatory for affixing theelectronic signature to the electronic document via the first electroniccommunication pathway; and upon notification of the affixing of theelectronic signature to the electronic document, transmit theelectronically signed electronic document to the second entity via thesecond electronic communication pathway.
 2. The system of claim 1,wherein the electronic document comprises an electronic signatureapplied by a signatory to a location on each of the documents thatcorresponds to a predetermined field tab.
 3. The system of claim 1,wherein the protocol comprises a ranking of authorized signatoriesdefined by two or more predetermined metrics.
 4. The system of claim 3,wherein the two or more of the predetermined metrics comprises the levelof availability of the authorized signatories and the seniority of theauthorized signatories.
 5. The system of claim 1, wherein, when theprotocol determines that a selected signatory is not available forelectronic signature, the protocol requires signature by two or moreauthorized signatories on the electronic document.